We have decided to work on a feature request for Shotwell listed here. The feature request deals with syncing Shotwell and Ubuntu One. Ubuntu One is a free cloud service that allows users to upload media to the cloud. With this feature a user can install the Ubuntu One application on their phone, take a picture, and that picture will automatically be synced to their Shotwell database in a special section. This feature is similar to Apple's iCloud service. Below is a tentative schedule for the rest of the semester, which will evolve as the project progresses:
Current Progress:
Our weekly Sunday meeting was successful in creating a stricter schedule for the rest of the semester. The current progress of week one is we have successfully applied to being assigned the project. We are waiting on the response from the Yorba team so that we may begin our development process. We have downloaded the Ubuntu One app on our phones and seen how it interacts with our own personal computers.
Change of Plans:
We told the Shotwell team of our plans to implement the Ubuntu One functionality. Unfortunately, this feature won't be able to be implemented given the way plugins operate within Shotwell currently. We now need to decide on another feature or set of bugs to fix. Right now we are thinking about all taking on an individual bug and also working on a larger bug or feature together. The 0.12 version of Shotwell was supposed to be released two weeks ago but it hasn't been pushed out yet. By us all taking on a bug individually we could help the new version of Shotwell get out of the door quicker. Once we decide on what we want to do we will have to revise our calendar to reflect these changes.
Update:
We have decided that we are going to work on a series of bugs within Shotwell. We also decided that working on these bugs as a team was the best course of action. Working on bugs individually may have resulted in more bugs being fixed, but we decided it was more important that the whole group be present for each bug to better assist each other and ensure the quality of our bug fixes.
Moving forward, we will be keeping to the goal of fixing one bug per week. The calendar above will be updated to show our new timeline. Team meetings have proven to be a successful tool in fixing bugs, so we will continue to meet as a group as least once a week.
For week one, we had to first solve a bug in the build process of Shotwell. We were unable to build the latest version of Shotwell due to a version problem with one Shotwell's dependencies. Our initial plan had been to fix another bug, but with the arrival of this bug, we were forced to fix it before proceeding with any other bug fixes. Never the less, this was a various serious bug, and having a workaround will allow us to continue with our plan.
Progress 03/19/2012
We initially decided to work on a feature request that After submitting our idea to the Shotwell team it was decided that the feature could not be implemented as a plugin. The plugin system that Shotwell uses can't handle publishing photos to an external service yet so this feature will have to wait. Instead we have decided to go with fixed a bug per week while also working on personal bugs if time permits. This will help both Shotwell and us. Shotwell is trying to push out a new version (0.12) and they need as many bugs fixed as possible. This also helps us in being able to work on the bugs on our own time during the week. We can also meet on Sundays to tie up any loose ends.
Bug #4094 This bug describes the behavior of a tool window (cropping, adjusting properties) whenever Shotwell is resized. If you maximize and minimize Shotwell when a tool window is open then the tool window does not stay centered. This can be fixed by resetting the tool window position every time Shotwell is resized. The tool windows are Gtk.Windows which has a method called "gtk_window_set_position ()". We are working on finding what the main window in Shotwell is called so that we can grab its position on the screen so then the tool windows position can be set.
Bug #3883 This bug describes how the undo function is not changing the current image to the deleted image after Undo-ing when Shotwell is in Fullscreen mode. Otherwise, the undo function makes the image reappear. This could be fixed by making the previous image the main image after pressing Ctrl+Z. The undo function works normally when it is not in fullscreen mode, so I would need to make sure that it does not switch into fullscreen after undo-ing. I'm currently trying to find where the Undo function is located inside of Shotwell.
Progress 03/27/2012
We again ran in to some trouble getting Shotwell to build after updating our working copies to the newest version from Yorba. We got a very timely response from the Shotwell Developers that resolved the issue. Unfortunately, the error arose during a group meeting, severely limited what we were able to accomplish during the meeting. Despite the setback, we still have a good amount to discuss, especially successfully fixing a bug.
Bug #4855
This bug has been fixed. A menu item named "New Search..." needed to be renamed "New Saved Search...". Since Shotwell saves all of the searches that you make it adds to the user friendliness of Shotwell and lets you know what is happening when you search.
Bug #4094 is still a work in progress. We thought that setting the position of a window in its constructor would let us position the window where we needed. This has proven not to be the case. Shotwell uses GTK 3 while the only official documentation for GTK is version 2. There is some documentation in a Valadoc but the descriptions are light if any at all. We will continue to work on this bug unless it looks unrealistic.
Feature #3612
We have also begun to investigate a feature addition that seem pretty straightforward. While perusing the bug tracker for workable bugs, we came across a feature request to add additional boolean searches to the project. the request offers some ideas as to what should be added as new search criteria. The feature request asks for functionality to search by camera type, whether or not an image has been edited, orientation, resolution, file size, aperture, shutter speed, and focal length. We have found where the boolean searches are coded, and extrapolating from existing searches, we should be able to implement new searches without much trouble.
Progress 04/02/2012
Bug #4855
This bug was patched, submitted, and approved by the Yorba Development Team. This bug was an aesthetic change to the text of the Edit menu. The text was changed to read "New Saved Search...". Bug #4413
This bug relates to cropping a photo to a standard paper size, 8.5 x 11. Currently Shotwell doesn't let you use a custom sizes that contain decimal values. Only integer values are allowed. The text box does not allow the user to enter a "." character so the user can never enter 8.5. Feature #3553
This feature request would extend the functionality of the searching the photo database by adding boolean logic like AND/OR. Bug #3274
This bug related to the separation between the main photo window and the search toolbar. Due to color similarities, it was difficult to tell where the toolbar ended and the photo window began. The spacing between the two has been increased so that the boundary between the two is more clear. A patch has been added to the bug, but there has not been an update from the Shotwell team as of yet.
Current Progress:
Our weekly Sunday meeting was successful in creating a stricter schedule for the rest of the semester. The current progress of week one is we have successfully applied to being assigned the project. We are waiting on the response from the Yorba team so that we may begin our development process. We have downloaded the Ubuntu One app on our phones and seen how it interacts with our own personal computers.Change of Plans:
We told the Shotwell team of our plans to implement the Ubuntu One functionality. Unfortunately, this feature won't be able to be implemented given the way plugins operate within Shotwell currently. We now need to decide on another feature or set of bugs to fix. Right now we are thinking about all taking on an individual bug and also working on a larger bug or feature together. The 0.12 version of Shotwell was supposed to be released two weeks ago but it hasn't been pushed out yet. By us all taking on a bug individually we could help the new version of Shotwell get out of the door quicker. Once we decide on what we want to do we will have to revise our calendar to reflect these changes.Update:
We have decided that we are going to work on a series of bugs within Shotwell. We also decided that working on these bugs as a team was the best course of action. Working on bugs individually may have resulted in more bugs being fixed, but we decided it was more important that the whole group be present for each bug to better assist each other and ensure the quality of our bug fixes.Moving forward, we will be keeping to the goal of fixing one bug per week. The calendar above will be updated to show our new timeline. Team meetings have proven to be a successful tool in fixing bugs, so we will continue to meet as a group as least once a week.
For week one, we had to first solve a bug in the build process of Shotwell. We were unable to build the latest version of Shotwell due to a version problem with one Shotwell's dependencies. Our initial plan had been to fix another bug, but with the arrival of this bug, we were forced to fix it before proceeding with any other bug fixes. Never the less, this was a various serious bug, and having a workaround will allow us to continue with our plan.
Progress 03/19/2012
We initially decided to work on a feature request that After submitting our idea to the Shotwell team it was decided that the feature could not be implemented as a plugin. The plugin system that Shotwell uses can't handle publishing photos to an external service yet so this feature will have to wait. Instead we have decided to go with fixed a bug per week while also working on personal bugs if time permits. This will help both Shotwell and us. Shotwell is trying to push out a new version (0.12) and they need as many bugs fixed as possible. This also helps us in being able to work on the bugs on our own time during the week. We can also meet on Sundays to tie up any loose ends.
Bug #4094
This bug describes the behavior of a tool window (cropping, adjusting properties) whenever Shotwell is resized. If you maximize and minimize Shotwell when a tool window is open then the tool window does not stay centered. This can be fixed by resetting the tool window position every time Shotwell is resized. The tool windows are Gtk.Windows which has a method called "gtk_window_set_position ()". We are working on finding what the main window in Shotwell is called so that we can grab its position on the screen so then the tool windows position can be set.
Bug #3883
This bug describes how the undo function is not changing the current image to the deleted image after Undo-ing when Shotwell is in Fullscreen mode. Otherwise, the undo function makes the image reappear. This could be fixed by making the previous image the main image after pressing Ctrl+Z. The undo function works normally when it is not in fullscreen mode, so I would need to make sure that it does not switch into fullscreen after undo-ing. I'm currently trying to find where the Undo function is located inside of Shotwell.
Progress 03/27/2012
We again ran in to some trouble getting Shotwell to build after updating our working copies to the newest version from Yorba. We got a very timely response from the Shotwell Developers that resolved the issue. Unfortunately, the error arose during a group meeting, severely limited what we were able to accomplish during the meeting. Despite the setback, we still have a good amount to discuss, especially successfully fixing a bug.
Bug #4855
This bug has been fixed. A menu item named "New Search..." needed to be renamed "New Saved Search...". Since Shotwell saves all of the searches that you make it adds to the user friendliness of Shotwell and lets you know what is happening when you search.
Bug #4094 is still a work in progress. We thought that setting the position of a window in its constructor would let us position the window where we needed. This has proven not to be the case. Shotwell uses GTK 3 while the only official documentation for GTK is version 2. There is some documentation in a Valadoc but the descriptions are light if any at all. We will continue to work on this bug unless it looks unrealistic.
Feature #3612
We have also begun to investigate a feature addition that seem pretty straightforward. While perusing the bug tracker for workable bugs, we came across a feature request to add additional boolean searches to the project. the request offers some ideas as to what should be added as new search criteria. The feature request asks for functionality to search by camera type, whether or not an image has been edited, orientation, resolution, file size, aperture, shutter speed, and focal length. We have found where the boolean searches are coded, and extrapolating from existing searches, we should be able to implement new searches without much trouble.
Progress 04/02/2012
Bug #4855This bug was patched, submitted, and approved by the Yorba Development Team. This bug was an aesthetic change to the text of the Edit menu. The text was changed to read "New Saved Search...".
Bug #4413
This bug relates to cropping a photo to a standard paper size, 8.5 x 11. Currently Shotwell doesn't let you use a custom sizes that contain decimal values. Only integer values are allowed. The text box does not allow the user to enter a "." character so the user can never enter 8.5.
Feature #3553
This feature request would extend the functionality of the searching the photo database by adding boolean logic like AND/OR.
Bug #3274
This bug related to the separation between the main photo window and the search toolbar. Due to color similarities, it was difficult to tell where the toolbar ended and the photo window began. The spacing between the two has been increased so that the boundary between the two is more clear. A patch has been added to the bug, but there has not been an update from the Shotwell team as of yet.
Related Links: